Skip to content

add handling of different lengths of scalarTags and correct Usage in ReadMe #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Strandtasche
Copy link

Hey,

I've used your script and noticed some things that might be improved.
In one of my examples the scalar "global steps / sec" is slightly shorter than the first column.
in your version the script crashes with an index error, so I added some error handling (substituting the missing values with NaN)

I also noticed some typos in your readme, which I fixed.

Thanks for the script, it helped me a lot

@anderskm
Copy link
Owner

anderskm commented Aug 7, 2018

@Strandtasche Thank you for submitting your pull request. I'm glad you have found the script helpful :-)
Could you provide a minimum working example, which produces different lengths of scalarTags?
That will help me test the code - both now and in the future.

@Strandtasche
Copy link
Author

What kind of example do you want? Do you want an tfevents file that has that property or some python/tensorflow code that generates an tfevents file that has different lengths of scalarTags?

@anderskm
Copy link
Owner

@Strandtasche Some python/tensorflow code is preferable :-)

@Strandtasche
Copy link
Author

Sorry for the delay. I didn't manage to produce a minimal working example. I don't even know why my code produces different lengths of scalarTags, maybe I made a mistake somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants